Summary

Reverts the client-side Sentry integration merged in #642, as requested. Removes:

• @sentry/browser dependency
• the same-origin tunnel route src/app/api/monitoring/route.ts
• src/lib/observability/sentry-client.ts + sentry-scrub.ts and tests/sentry-client.test.ts
• the gated client init in src/instrumentation-client.ts (back to just the Zod jitless config) and the __SENTRY_ENABLED__ DefinePlugin in next.config.ts
• NEXT_PUBLIC_SENTRY_DSN / NEXT_PUBLIC_SENTRY_ENVIRONMENT from env.ts
• the captureClientException wiring in the route + global error boundaries

Server-side error capture is untouched — @sentry/node via src/lib/observability/error-capture.ts + src/instrumentation.ts (gated on SENTRY_DSN) predates #642 and remains, fully inert without a DSN.

Done as a clean git revert of the #642 squash commit (71d9f2c76); no conflicts.

Verification

• ✅ typecheck, lint — clean
• ✅ build — exit 0; no @sentry / sentry-scrub / sentry-client / __SENTRY_ENABLED__ in the client bundle; /api/monitoring route absent from build output
• ✅ test — 2298 pass (the 3 "failures" were Test timed out flakes from a concurrent build starving the AST-graph tests; both files pass 10/10 when re-run in isolation)
• ✅ No lingering client-Sentry references anywhere in src/tests/next.config.ts

Clinical Governance Preflight

N/A — removes an observability integration; no ingestion, answer generation, search, privacy, or clinical output behavior changes. (The client tunnel and its public DSN are gone; server capture behavior is unchanged.)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Changes

  • Removed client-side error reporting to Sentry; application errors are now logged locally while existing recovery options remain available.
  • Removed the monitoring endpoint used to forward error reports.
  • Removed related Sentry browser configuration and environment settings.

• Documentation

  • Updated the API route documentation to remove the retired monitoring endpoint.